Patching
Introduction
Versioning plays a major role in yeet. We strive to provide continuous updates that fix bugs and introduce new features.
Sometimes this also means that existing behavior changes or is improved.
How patching works
When you work with a specific version of yeet, any resources you create – such as projects and themes – are tagged with that version.
This ensures a safe working environment, because it clearly marks the yeet version your project is based on.
When a new version is released, your existing projects need to be patched to that version to stay compatible with the development environment and all of its features.
-
Without patching
Your application continues to run, but you can no longer develop it further in the current yeet version because the project’s version lags behind. -
After patching
Your application is upgraded to the new version, and you can continue development using the latest features and fixes.
When should I patch?
Patching your project is the best way to keep your development process aligned with the platform and to benefit from bug fixes and improvements.
We recommend applying patches regularly whenever new yeet releases are rolled out.
Whenever you upgrade yeet to a new version, you should:
- Run the patching process for all existing projects that you still actively maintain.
- Test the fully patched version of your application before rolling it out to end users, to ensure that everything still works as expected.